Fortinet FortiNDR Cloud
Browse: 🏠 · Solutions · Connectors · Methods · Tables · Content · Parsers · ASIM Parsers · ASIM Products · 📊
| Attribute | Value |
|---|---|
| Connector ID | FortinetFortiNdrCloudDataConnector |
| Publisher | Fortinet |
| Used in Solutions | Fortinet FortiNDR Cloud |
| Collection Method | Azure Function |
| Connector Definition Files | FortinetFortiNdrCloud_API_AzureFunctionApp.json |
| Ingestion API | HTTP Data Collector API — Azure Function code uses SharedKey/HTTP Data Collector API |
| Custom Log V1 Tables | Yes 🔶 — ingests into tables with type-suffixed columns |
The Fortinet FortiNDR Cloud data connector provides the capability to ingest Fortinet FortiNDR Cloud data into Microsoft Sentinel using the FortiNDR Cloud API
Tables Ingested
This connector ingests data into the following tables:
| Table | Transformations | Ingestion API | Lake-Only |
|---|---|---|---|
FncEventsDetections_CL 🔶 |
? | ✓ | ? |
FncEventsObservation_CL 🔶 |
? | ✓ | ? |
FncEventsSuricata_CL 🔶 |
? | ✓ | ? |
💡 Tip: Tables with Ingestion API support allow data ingestion via the Azure Monitor Data Collector API, which also enables custom transformations during ingestion.
Permissions
Resource Provider Permissions: - Workspace (Workspace): read and write permissions on the workspace are required. - Keys (Workspace): read permissions to shared keys for the workspace are required. See the documentation to learn more about workspace keys.
Custom Permissions: - Microsoft.Web/sites permissions: Read and write permissions to Azure Functions to create a Function App is required. See the documentation to learn more about Azure Functions. - MetaStream Credentials: AWS Access Key Id, AWS Secret Access Key, FortiNDR Cloud Account Code are required to retrieve event data. - API Credentials: FortiNDR Cloud API Token, FortiNDR Cloud Account UUID are required to retrieve detection data.
Setup Instructions
⚠️ Note: These instructions were automatically generated from the connector's user interface definition file using AI and may not be fully accurate. Please verify all configuration steps in the Microsoft Sentinel portal.
NOTE: This connector uses Azure Functions to connect to the FortiNDR Cloud API to pull logs into Microsoft Sentinel. This might result in additional data ingestion costs. Check the Azure Functions pricing page for details.
(Optional Step) Securely store workspace and API authorization key(s) or token(s) in Azure Key Vault. Azure Key Vault provides a secure mechanism to store and retrieve key values. Follow these instructions to use Azure Key Vault with an Azure Function App.
NOTE: This connector uses a parser based on a Kusto Function to normalize fields. Follow these steps to create the Kusto function alias Fortinet_FortiNDR_Cloud.
STEP 1 - Configuration steps for the Fortinet FortiNDR Cloud Logs Collection
The provider should provide or link to detailed steps to configure the 'PROVIDER NAME APPLICATION NAME' API endpoint so that the Azure Function can authenticate to it successfully, get its authorization key or token, and pull the appliance's logs into Microsoft Sentinel.
STEP 2 - Choose ONE from the following two deployment options to deploy the connector and the associated Azure Function
IMPORTANT: Before deploying the Fortinet FortiNDR Cloud connector, have the Workspace ID and Workspace Primary Key (can be copied from the following), as well as the as well as the FortiNDR Cloud API credentials (available in FortiNDR Cloud account management), readily available. - Workspace ID:
WorkspaceIdNote: The value above is dynamically provided when these instructions are presented within Microsoft Sentinel. - Primary Key:PrimaryKeyNote: The value above is dynamically provided when these instructions are presented within Microsoft Sentinel.
Azure Resource Manager (ARM) Template
Use this method for automated deployment of the Fortinet FortiNDR Cloud connector.
-
Click the Deploy to Azure button below.
2. Select the preferred Subscription, Resource Group and Location(Make sure using the same location as your Resource Group, and got the location supports Flex Consumption. 3. Enter the Workspace ID, Workspace Key, AwsAccessKeyId, AwsSecretAccessKey, and/or Other required fields. 4. Click Create to deploy.
Browse: 🏠 · Solutions · Connectors · Methods · Tables · Content · Parsers · ASIM Parsers · ASIM Products · 📊